kashrut requirements - перевод на итальянский
DICLIB.COM
Языковые инструменты на ИИ
Введите слово или словосочетание на любом языке 👆
Язык:     

Перевод и анализ слов искусственным интеллектом

На этой странице Вы можете получить подробный анализ слова или словосочетания, произведенный с помощью лучшей на сегодняшний день технологии искусственного интеллекта:

  • как употребляется слово
  • частота употребления
  • используется оно чаще в устной или письменной речи
  • варианты перевода слова
  • примеры употребления (несколько фраз с переводом)
  • этимология

kashrut requirements - перевод на итальянский

PROCESS OF DEFINING, DOCUMENTING, AND MAINTAINING REQUIREMENTS IN THE ENGINEERING DESIGN PROCESS
Requirements Engineering; Requirement engineering; Requirements engineer

kashrut requirements      
leggi sulla cashrut
software requirements         
Software Requirements
(informatica) il software necessario , elenco dei software richiesti (per realizzazioni efficienti); le esigenze di un programma, per quel che riguarda il software e l"hardware, per un lavoro efficace
user friendly         
  • Many [[tool]]s are designed to be easy to hold and use for their intended purpose. For example, a [[screwdriver]] typically has a handle with rounded edges and a grippable surface, to make it easier for the user to hold the handle and twist it to drive a screw.
LEARNABILITY AND EASE-OF-USE OF A HELPFUL TOOL, SYSTEM, ETC. INTENDED FOR HUMAN USE
User-friendliness; Software usability; User friendliness; Userfriendliness; Ease of use; Usabilidade; Usability Requirements; Product usability; Usable; Unusable; Useable; Useability; User friendly; User-friendly; Usability requirements; Evaluation of usability
di facile uso, maneggevole

Определение

requirements analysis
<project> The process of reviewing a business's processes to determine the business needs and functional requirements that a system must meet. (1996-08-01)

Википедия

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering.

The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

In the waterfall model, requirements engineering is presented as the first phase of the development process. Later development methods, including the Rational Unified Process (RUP) for software, assume that requirements engineering continues through a system's lifetime.

Requirements management, which is a sub-function of Systems Engineering practices, is also indexed in the International Council on Systems Engineering (INCOSE) manuals.